-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Outreachy] Removed ipv6 fallback #1900
[Outreachy] Removed ipv6 fallback #1900
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can confirm that the code works as expected, and I suggested a couple of changes, so we're close.
@dscho squashed commits and revised the commit message. |
I just started a rebuild, as I am worried that the loooong run time of the test suite might be somehow caused by this patch. Admittedly, I was unable to spot anything wrong, from my perspective this PR should be ready (and pass the test suite in the regular time). |
That's really bad. And it is consistently failing with this PR, for the same reason: it times out after 4h (!!!). Quite honestly, I have no idea why/where the problem lies, but since it happens with this PR only, it must be caused by the changes introduced by this PR... Very strange. |
To support IPv6, Git provided fall back functions for Windows versions that did not support IPv6. However, as Git dropped support for Windows XP and prior, those functions are not needed anymore. Removed those fallbacks by reverting commit[1] and using the functions directly (without 'ipv6_' prefix). [1] fe3b2b7. Signed-off-by: tanushree27 <[email protected]>
Ah! In 28f1d8e you removed the shims altogether, and with them, the socket initialization. I would wager a guess that that makes the difference, and that we do not even need to initialize the socket system to look up IPv6 addresses? But why, then, do we look up IPv6 addresses so often that it slows down the test suite noticeably? |
In 8cf11a9 I commented out shims, and this worked like a charm build #20181113.7. However, when I removed the shims in 28f1d8e the tests suite failed. |
You refer to https://git-for-windows.visualstudio.com/git/_build/results?buildId=24879&view=logs, correct? If so, the Could you re-push 28f1d8e? |
Yes, I was referring to this.
Done. |
And now the tests pass ;-) |
…fallback [Outreachy] Removed ipv6 fallback
…fallback [Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
…fallback [Outreachy] Removed ipv6 fallback
…fallback [Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
[Outreachy] Removed ipv6 fallback
ipv6_*
callers by non-prefixed versions.ipv6_*
pointer functions and stub functions.ensure_socket_initialization
.